use Bicep loop syntax to create spoke resources the same way #497
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change creates spokes and their dependencies in the same way to reduce the likelihood of introducing changes that causes spokes to differ.
First, it creates a
mlz.bicep
array calledspokes
that is composed of user-defined and defaulted parameters:missionlz/src/bicep/mlz.bicep
Lines 557 to 561 in d95dc7a
Then, it uses Bicep's loop syntax to create modules for those items in the
spokes
array:missionlz/src/bicep/mlz.bicep
Lines 17 to 25 in d95dc7a
This change also adds documentation on how to retrieve deployed resources programmatically:
https://github.com/Azure/missionlz/blob/d95dc7a43a32260fe6532fab1b313c2f7cff764e/src/bicep/README.md#reference-deployment-output
Issue reference
The issue this PR will close: #493
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list: